The IDPS must be capable of taking organizationally defined actions upon audit failure.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-34555	SRG-NET-000089-IDPS-00069	SV-45397r1_rule		Low

Description
Auditing of account use and user actions is a critical part of the security architecture. Auditable events must be logged. If the IDPS becomes unable to write events to the audit log, this is known as an audit processing failure. Audit processing failures include software and hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. To preserve recent audit information, if an audit failure occurs, the IDPS must stop producing audit records, overwrite older records, or purge the oldest records.

Description

Auditing of account use and user actions is a critical part of the security architecture. Auditable events must be logged. If the IDPS becomes unable to write events to the audit log, this is known as an audit processing failure. Audit processing failures include software and hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. To preserve recent audit information, if an audit failure occurs, the IDPS must stop producing audit records, overwrite older records, or purge the oldest records.

STIG	Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide	2012-11-19

Details

Check Text ( C-42746r1_chk )
Review the IDPS configuration to determine if specific actions, as defined by the organization, are taken when an audit process fails. If specific actions are not taken upon audit failure, this is a finding.

Fix Text (F-38794r1_fix)
Configure the IDPS components to take specific actions, as defined by the organization, when an audit process fails.